Flexible buffer management for optimizing congestion control using radio access network intelligent controller for 5g or other next generation wireless network

ABSTRACT

Flexible buffer management is provided that optimizes congestion control using a radio access network (RAN) intelligent controller. A system can comprise monitoring a performance of a communication traffic flow using a group of buffer parameters of a network node device of a wireless network, wherein the performance is measured according to a defined performance criterion, receiving performance values for requested performance characteristics of the performance of the communication traffic flow via a first interface, and based on an adjustment value of the performance values, adjusting, via a second interface, a buffer parameter of the group of buffer parameters.

RELATED APPLICATION

The subject patent application is a continuation of, and claims priorityto, U.S. patent application Ser. No. 16/518,956, filed Jul. 22, 2019,and entitled “FLEXIBLE BUFFER MANAGEMENT FOR OPTIMIZING CONGESTIONCONTROL USING RADIO ACCESS NETWORK INTELLIGENT CONTROLLER FOR 5G OROTHER NEXT GENERATION WIRELESS NETWORK,” the entirety of whichapplication is hereby incorporated by reference herein.

TECHNICAL FIELD

This disclosure relates generally to buffer management, and, morespecifically, to facilitating flexible buffer management for optimizingcongestion control using radio access network (RAN) intelligentcontroller, e.g., for 5th generation (5G) or other next generationwireless network.

BACKGROUND

5G wireless systems represent a next major phase of mobiletelecommunications standards beyond the current telecommunicationsstandards of 4^(th) generation (4G). In addition to faster peak Internetconnection speeds, 5G planning aims at higher capacity than current 4G,allowing a higher number of mobile broadband users per area unit, andallowing consumption of higher or unlimited data quantities. This wouldenable a large portion of the population to stream high-definition mediamany hours per day with their mobile devices, when out of reach ofwireless fidelity hotspots. 5G research and development also aims atimproved support of machine-to-machine communication, also known as theInternet of Things, aiming at lower cost, lower battery consumption, andlower latency than 4G equipment. Latency over RAN is a major factor thataffects the end-to-end latency and performance over applications overcellular networks. The upcoming 5G networks promise high throughput andlow latency radio access through mmWave radio, flexible RAN, and edgeclouds. However, a key factor that affects throughput and latency ofapplications besides the RAN is application-layer congestion controlworking in tandem with the RAN. Traditional flavors of transmissioncontrol protocol (TCP) don't perform well under varying radio linkqualities, congestion, and buffering at the network node devices. Thereare several congestion control algorithms that aim to overcome problemswith traditional flavors of TCP. Most of these algorithms treat theunderlying network as a black box and aim to maximize an underlyingutility function to maximize throughput and/or reduce latency.

The above-described background relating to relating to latency in the 5Gcommunication system, is merely intended to provide a contextualoverview of some current issues, and is not intended to be exhaustive(e.g., although problems and solution are directed to next generationnetworks such as 5G, the solutions can be applied to 4G/LTEtechnologies). Other contextual information may become further apparentupon review of the following detailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

Non-limiting and non-exhaustive embodiments of the subject disclosureare described with reference to the following figures, wherein likereference numerals refer to like parts throughout the various viewsunless otherwise specified.

FIG. 1 illustrates an example wireless communication system in which anetwork node device and user equipment (UE) can implement variousaspects and embodiments of the subject disclosure.

FIG. 2 illustrates an example schematic system block diagram ofintegrated access and backhaul links according to one or moreembodiments.

FIG. 3 illustrates an example of RAN network architecture in accordancewith various aspects and embodiments described herein.

FIG. 4 illustrates an example of a buffer control algorithm that canfacilitate optimizing congestion control using radio access network(RAN) intelligent controller in accordance with various aspects andembodiments described herein.

FIG. 5 illustrates a block diagram of an example, non-limiting systemthat facilitates flexible buffer management for optimizing congestioncontrol using radio access network (RAN) intelligent controller inaccordance with one or more embodiments described herein.

FIG. 6 depicts a diagram of an example, non-limiting computerimplemented method that facilitates flexible buffer management foroptimizing congestion control using radio access network (RAN)intelligent controller in accordance with one or more embodimentsdescribed herein.

FIG. 7 depicts a diagram of an example, non-limiting computerimplemented method that facilitates flexible buffer management foroptimizing congestion control using radio access network (RAN)intelligent controller in accordance with one or more embodimentsdescribed herein.

FIG. 8 depicts a diagram of an example, non-limiting computerimplemented method that facilitates flexible buffer management foroptimizing congestion control using radio access network (RAN)intelligent controller in accordance with one or more embodimentsdescribed herein.

FIG. 9 depicts a diagram of an example, non-limiting computerimplemented method that facilitates flexible buffer management foroptimizing congestion control using radio access network (RAN)intelligent controller in accordance with one or more embodimentsdescribed herein.

FIG. 10 illustrates an example block diagram of an example computeroperable to engage in a system architecture that facilitates securewireless communication according to one or more embodiments describedherein.

DETAILED DESCRIPTION

In the following description, numerous specific details are set forth toprovide a thorough understanding of various embodiments. One skilled inthe relevant art will recognize, however, that the techniques describedherein can be practiced without one or more of the specific details, orwith other methods, components, materials, etc. In other instances,well-known structures, materials, or operations are not shown ordescribed in detail to avoid obscuring certain aspects.

Reference throughout this specification to “one embodiment,” or “anembodiment,” means that a particular feature, structure, orcharacteristic described in connection with the embodiment is includedin at least one embodiment. Thus, the appearances of the phrase “in oneembodiment,” “in one aspect,” or “in an embodiment,” in various placesthroughout this specification are not necessarily all referring to thesame embodiment. Furthermore, the particular features, structures, orcharacteristics may be combined in any suitable manner in one or moreembodiments.

As utilized herein, terms “component,” “system,” “interface,” and thelike are intended to refer to a computer-related entity, hardware,software (e.g., in execution), and/or firmware. For example, a componentcan be a processor, a process running on a processor, an object, anexecutable, a program, a storage device, and/or a computer. By way ofillustration, an application running on a server and the server can be acomponent. One or more components can reside within a process, and acomponent can be localized on one computer and/or distributed betweentwo or more computers.

Further, these components can execute from various machine-readablemedia having various data structures stored thereon. The components cancommunicate via local and/or remote processes such as in accordance witha signal having one or more data packets (e.g., data from one componentinteracting with another component in a local system, distributedsystem, and/or across a network, e.g., the Internet, a local areanetwork, a wide area network, etc. with other systems via the signal).

As another example, a component can be an apparatus with specificfunctionality provided by mechanical parts operated by electric orelectronic circuitry; the electric or electronic circuitry can beoperated by a software application or a firmware application executed byone or more processors; the one or more processors can be internal orexternal to the apparatus and can execute at least a part of thesoftware or firmware application. As yet another example, a componentcan be an apparatus that provides specific functionality throughelectronic components without mechanical parts; the electroniccomponents can include one or more processors therein to executesoftware and/or firmware that confer(s), at least in part, thefunctionality of the electronic components. In an aspect, a componentcan emulate an electronic component via a virtual machine, e.g., withina cloud computing system.

The words “exemplary” and/or “demonstrative” are used herein to meanserving as an example, instance, or illustration. For the avoidance ofdoubt, the subject matter disclosed herein is not limited by suchexamples. In addition, any aspect or design described herein as“exemplary” and/or “demonstrative” is not necessarily to be construed aspreferred or advantageous over other aspects or designs, nor is it meantto preclude equivalent exemplary structures and techniques known tothose of ordinary skill in the art. Furthermore, to the extent that theterms “includes,” “has,” “contains,” and other similar words are used ineither the detailed description or the claims, such terms are intendedto be inclusive—in a manner similar to the term “comprising” as an opentransition word—without precluding any additional or other elements.

As used herein, the term “infer” or “inference” refers generally to theprocess of reasoning about, or inferring states of, the system,environment, user, and/or intent from a set of observations as capturedvia events and/or data. Captured data and events can include user data,device data, environment data, data from sensors, sensor data,application data, implicit data, explicit data, etc. Inference can beemployed to identify a specific context or action, or can generate aprobability distribution over states of interest based on aconsideration of data and events, for example.

Inference can also refer to techniques employed for composinghigher-level events from a set of events and/or data. Such inferenceresults in the construction of new events or actions from a set ofobserved events and/or stored event data, whether the events arecorrelated in close temporal proximity, and whether the events and datacome from one or several event and data sources. Various classificationschemes and/or systems (e.g., support vector machines, neural networks,expert systems, Bayesian belief networks, fuzzy logic, and data fusionengines) can be employed in connection with performing automatic and/orinferred action in connection with the disclosed subject matter.

In addition, the disclosed subject matter can be implemented as amethod, apparatus, or article of manufacture using standard programmingand/or engineering techniques to produce software, firmware, hardware,or any combination thereof to control a computer to implement thedisclosed subject matter. The term “article of manufacture” as usedherein is intended to encompass a computer program accessible from anycomputer-readable device, machine-readable device, computer-readablecarrier, computer-readable media, or machine-readable media. Forexample, computer-readable media can include, but are not limited to, amagnetic storage device, e.g., hard disk; floppy disk; magneticstrip(s); an optical disk (e.g., compact disk (CD), a digital video disc(DVD), a Blu-ray Disc™ (BD)); a smart card; a flash memory device (e.g.,card, stick, key drive); and/or a virtual device that emulates a storagedevice and/or any of the above computer-readable media.

As an overview, various embodiments are described herein to facilitateflexible buffer management for optimizing congestion control using radioaccess network (RAN) intelligent controller. For simplicity ofexplanation, the methods (or algorithms) are depicted and described as aseries of acts. It is to be understood and appreciated that the variousembodiments are not limited by the acts illustrated and/or by the orderof acts. For example, acts can occur in various orders and/orconcurrently, and with other acts not presented or described herein.Furthermore, not all illustrated acts may be required to implement themethods. In addition, the methods could alternatively be represented asa series of interrelated states via a state diagram or events.Additionally, the methods described hereafter are capable of beingstored on an article of manufacture (e.g., a machine-readable storagemedium) to facilitate transporting and transferring such methodologiesto computers. The term article of manufacture, as used herein, isintended to encompass a computer program accessible from anycomputer-readable device, carrier, or media, including a non-transitorymachine-readable storage medium.

It should be noted that although various aspects and embodiments havebeen described herein in the context of 5G, Universal MobileTelecommunications System (UMTS), and/or Long-Term Evolution (LTE), orother next generation networks, the disclosed aspects are not limited to5G, a UMTS implementation, and/or an LTE implementation as thetechniques can also be applied in 3G, 4G or LTE systems. For example,aspects or features of the disclosed embodiments can be exploited insubstantially any wireless communication technology. Such wirelesscommunication technologies can include UMTS, Code Division MultipleAccess (CDMA), Wi-Fi, Worldwide Interoperability for Microwave Access(WiMAX), General Packet Radio Service (GPRS), Enhanced GPRS, ThirdGeneration Partnership Project (3GPP), LTE, Third Generation PartnershipProject 2 (3GPP2) Ultra Mobile Broadband (UMB), High Speed Packet Access(HSPA), Evolved High Speed Packet Access (HSPA+), High-Speed DownlinkPacket Access (HSDPA), High-Speed Uplink Packet Access (HSUPA), Zigbee,or another IEEE 802.XX technology. Additionally, substantially allaspects disclosed herein can be exploited in legacy telecommunicationtechnologies.

Described herein are systems, methods, articles of manufacture, andother embodiments or implementations that can facilitate dynamicreconfiguration of 5G backhaul connection upon detecting a connectionfailure. Facilitating dynamic reconfiguration of 5G backhaul connectioncan be implemented in connection with any type of device with aconnection to the communications network (e.g., a mobile handset, acomputer, a handheld device, etc.) any Internet of Things (IoT) device(e.g., toaster, coffee maker, blinds, music players, speakers, etc.),and/or any connected vehicles (cars, airplanes, space rockets, and/orother at least partially automated vehicles (e.g., drones)). In someembodiments the non-limiting term user equipment (UE) is used. It canrefer to any type of wireless device that communicates with a radionetwork node in a cellular or mobile communication system. Examples ofUE are target device, device to device (D2D) UE, machine type UE or UEcapable of machine to machine (M2M) communication, PDA, Tablet, mobileterminals, smart phone, laptop embedded equipped (LEE), laptop mountedequipment (LME), USB dongles, etc. Note that the terms element, elementsand antenna ports can be interchangeably used but carry the same meaningin this disclosure. The embodiments are applicable to single carrier aswell as to multicarrier (MC) or carrier aggregation (CA) operation ofthe UE. The term carrier aggregation (CA) is also called (e.g.,interchangeably called) “multi-carrier system”, “multi-cell operation”,“multi-carrier operation”, “multi-carrier” transmission and/orreception.

In some embodiments the non-limiting term radio, network node device, orsimply network node is used. It can refer to any type of network nodethat serves UE is connected to other network nodes or network elementsor any radio node from where UE receives a signal. Examples of radionetwork nodes are Node B, base station (BS), multi-standard radio (MSR)node such as MSR BS, evolved Node B (eNB), next generation Node B (gNB),network controller, radio network controller (RNC), base stationcontroller (BSC), relay, donor node controlling relay, base transceiverstation (BTS), access point (AP), transmission points, transmissionnodes, remote radio unit (RRU), remote radio head (RRH), nodes indistributed antenna system (DAS), relay device, network node, nodedevice, etc.

Cloud radio access networks (RAN) can enable the implementation ofconcepts such as software-defined network (SDN) and network functionvirtualization (NFV) in 5G networks. This disclosure can facilitate ageneric channel state information framework design for a 5G network.Certain embodiments of this disclosure can comprise an SDN controllerthat can control routing of traffic within the network and between thenetwork and traffic destinations. The SDN controller can be merged withthe 5G network architecture to enable service deliveries via openapplication programming interfaces (“APIs”) and move the network coretowards an all internet protocol (“IP”), cloud based, and softwaredriven telecommunications network. The SDN controller can work with ortake the place of policy and charging rules function (“PCRF”) networkelements so that policies such as quality of service and trafficmanagement and routing can be synchronized and managed end to end.

The RAN Intelligent Controller (RIC) is a flexible platform that allowscontrol of RAN on a per UE (User Equipment) basis with very low latency(20 ms). A typical RIC deployment will control a few hundred eNBs orgNBs. The RIC will allow developers to deploy their own applications(e.g., xApps) to optimize the RAN for different use cases such as loadbalancing, dual connectivity etc. Through such RAN optimization, a keyexpectation for RIC is to enable high throughput, low-latencyapplications. In some embodiments, the RIC can influence congestioncontrol at the servers, is by sending information such as radio resourceavailability, eNB buffer status, UE channel quality directly to theserver. The server can then directly use this information to takeappropriate congestion control action.

All congestion control algorithms rely on measurements such as packetdrop rates, RTT (round trip time), or a congestion marker such as ECN tomake control decisions. According an embodiments, an intelligent buffermanagement through the RIC is used to influence the behavior ofcongestion control algorithms. Existing eNBs typically use deep buffersat the data plane where each bearer is allocated its own buffer. Thisapproach prioritizes using all available radio transmissionopportunities by keeping the transmission buffer full and has workedwell so far for web-browsing and video traffic. Dynamically adjustingthe queueing and scheduling policy at the eNB (e.g., changing buffersize, pro-actively dropping packets, or changing ECN marking threshold)can have a big impact on application performance. In some embodiments,the algorithm utilizes the RIC flexibly to control thequeuing/scheduling policy for a buffer. The RIC can switch betweenqueuing schemes, scheduling policies, or drop packets depending on theset of data plane techniques available at the eNB/gNB. The queueingschemes do not need to be available at the hardware stack of the eNB/gNBbut rather can be placed as small programmable hardware modules in frontof the actual bearer-specific queues. An eNB/gNB buffer management xApprunning on the RIC will monitor the RAN and the flow performance anddynamically tune the available policies through the E2 interface. ThexApp will run the algorithm to optimize the application performance. Theper-flow requirements of throughput, latency, or application burstcharacteristics are communicated to the xAPP through the A1 interface tothe RIC. In some embodiments, the RIC performs these optimizations notat a per-packet but at the order of tens of milliseconds to hundreds ofmilliseconds. This time horizon is long enough to get aggregate RANstatistics to the RIC and short enough such that the RIC can monitor anybursts in traffic and ensure low latency (order of tens ofmilliseconds).

According to some embodiments, the buffer management will improvelatency over handovers. During a handover, the eNB buffer is migratedfrom the source eNB to the target eNB over the X2 interface. The buffermanagement xApp can leverage techniques such as handover prediction topro-actively limit the buffer size when a handover is imminent. Thiswill reduce data-plane latency and core traffic on the mobile operator'snetwork.

According to some embodiments, the buffer control algorithm measures thethroughput and per-packet delay of each flow. The algorithm periodicallyperforms small experiments by changing the buffer sizes or queuingpolicy at a flow. Tuning the scheduling algorithm is performed at aslower time scale. The results of these experiments will be evaluated tosee if the flow meets its performance requirements of throughput andlatency. Using an online learning technique, the algorithm can explorethe state space and arrive at the optimal solution for each flow.

According an embodiment, a system can comprise a processor and a memorythat stores executable instructions that, when executed by theprocessor, facilitate performance of operations comprising monitoring aperformance of a communication traffic flow using a group of bufferparameters of a network node device of a wireless network, wherein theperformance is measured according to a defined performance criterion.The system can further facilitate receiving performance values forrequested performance characteristics of the performance of thecommunication traffic flow via a first interface. The system can furtherfacilitate based on an adjustment value of the performance values,adjusting, via a second interface, a buffer parameter of the group ofbuffer parameters.

According to another embodiment, described herein is a method that cancomprise monitoring, by a device comprising a processor, a communicationtraffic flow performance using a group of buffer parameters of a networknode device of a wireless network. The method can further comprisereceiving, by the device, required performance characteristics of thecommunication traffic flow performance via an interface. The method canfurther comprise based on performance values, adjusting, by the device,a buffer parameter of a network node device of the wireless networkbased on an adjustment value.

According to yet another embodiment, a device can comprise a processorand a memory that stores executable instructions that, when executed bythe processor, facilitate performance of operations comprisingmonitoring a performance of a flow of communication traffic using agroup of communication parameters of a network node. The device canfurther comprise receiving, via a first interface, requested performancecharacteristics of the performance of the flow of the communicationtraffic. The device can further comprise based on an adjustment value ofthe performance values, adjusting, via a second interface, acommunication parameter of the group of communication parameters.

These and other embodiments or implementations are described in moredetail below with reference to the drawings. Repetitive description oflike elements employed in the figures and other embodiments describedherein is omitted for sake of brevity.

FIG. 1 illustrates a non-limiting example of a wireless communicationsystem 100 in accordance with various aspects and embodiments of thesubject disclosure. In one or more embodiments, system 100 can compriseone or more user equipment UEs 102. The non-limiting term user equipmentcan refer to any type of device that can communicate with a network nodein a cellular or mobile communication system. A UE can have one or moreantenna panels having vertical and horizontal elements. Examples of a UEcomprise a target device, device to device (D2D) UE, machine type UE orUE capable of machine to machine (M2M) communications, personal digitalassistant (PDA), tablet, mobile terminals, smart phone, laptop mountedequipment (LME), universal serial bus (USB) dongles enabled for mobilecommunications, a computer having mobile capabilities, a mobile devicesuch as cellular phone, a laptop having laptop embedded equipment (LEE,such as a mobile broadband adapter), a tablet computer having a mobilebroadband adapter, a wearable device, a virtual reality (VR) device, aheads-up display (HUD) device, a smart car, a machine-type communication(MTC) device, and the like. User equipment UE 102 can also comprise IOTdevices that communicate wirelessly.

In various embodiments, system 100 is or comprises a wirelesscommunication network serviced by one or more wireless communicationnetwork providers. In example embodiments, a UE 102 can becommunicatively coupled to the wireless communication network via anetwork node 104. The network node (e.g., network node device) cancommunicate with user equipment (UE), thus providing connectivitybetween the UE and the wider cellular network. The UE 102 can sendtransmission type recommendation data to the network node 104. Thetransmission type recommendation data can comprise a recommendation totransmit data via a closed loop MIMO mode and/or a rank-1 precoder mode.

A network node can have a cabinet and other protected enclosures, anantenna mast, and multiple antennas for performing various transmissionoperations (e.g., MIMO operations). Network nodes can serve severalcells, also called sectors, depending on the configuration and type ofantenna. In example embodiments, the UE 102 can send and/or receivecommunication data via a wireless link to the network node 104. Thedashed arrow lines from the network node 104 to the UE 102 representdownlink (DL) communications and the solid arrow lines from the UE 102to the network nodes 104 represents an uplink (UL) communication.

System 100 can further include one or more communication serviceprovider networks 106 that facilitate providing wireless communicationservices to various UEs, including UE 102, via the network node 104and/or various additional network devices (not shown) included in theone or more communication service provider networks 106. The one or morecommunication service provider networks 106 can include various types ofdisparate networks, including but not limited to: cellular networks,femto networks, picocell networks, microcell networks, internet protocol(IP) networks Wi-Fi service networks, broadband service network,enterprise networks, cloud based networks, millimeter wave networks andthe like. For example, in at least one implementation, system 100 can beor include a large scale wireless communication network that spansvarious geographic areas. According to this implementation, the one ormore communication service provider networks 106 can be or include thewireless communication network and/or various additional devices andcomponents of the wireless communication network (e.g., additionalnetwork devices and cell, additional UEs, network server devices, etc.).The network node 104 can be connected to the one or more communicationservice provider networks 106 via one or more backhaul links 108. Forexample, the one or more backhaul links 108 can comprise wired linkcomponents, such as a T1/E1 phone line, a digital subscriber line (DSL)(e.g., either synchronous or asynchronous), an asymmetric DSL (ADSL), anoptical fiber backbone, a coaxial cable, and the like. The one or morebackhaul links 108 can also include wireless link components, such asbut not limited to, line-of-sight (LOS) or non-LOS links which caninclude terrestrial air-interfaces or deep space links (e.g., satellitecommunication links for navigation).

Wireless communication system 100 can employ various cellular systems,technologies, and modulation modes to facilitate wireless radiocommunications between devices (e.g., the UE 102 and the network node104). While example embodiments might be described for 5G new radio (NR)systems, the embodiments can be applicable to any radio accesstechnology (RAT) or multi-RAT system where the UE operates usingmultiple carriers e.g. LTE FDD/TDD, GSM/GERAN, CDMA2000 etc.

For example, system 100 can operate in accordance with global system formobile communications (GSM), universal mobile telecommunications service(UMTS), long term evolution (LTE), LTE frequency division duplexing (LTEFDD, LTE time division duplexing (TDD), high speed packet access (HSPA),code division multiple access (CDMA), wideband CDMA (WCMDA), CDMA2000,time division multiple access (TDMA), frequency division multiple access(FDMA), multi-carrier code division multiple access (MC-CDMA),single-carrier code division multiple access (SC-CDMA), single-carrierFDMA (SC-FDMA), orthogonal frequency division multiplexing (OFDM),discrete Fourier transform spread OFDM (DFT-spread OFDM) single carrierFDMA (SC-FDMA), Filter bank based multi-carrier (FBMC), zero tailDFT-spread-OFDM (ZT DFT-s-OFDM), generalized frequency divisionmultiplexing (GFDM), fixed mobile convergence (FMC), universal fixedmobile convergence (UFMC), unique word OFDM (UW-OFDM), unique wordDFT-spread OFDM (UW DFT-Spread-OFDM), cyclic prefix OFDM CP-OFDM,resource-block-filtered OFDM, Wi Fi, WLAN, WiMax, and the like. However,various features and functionalities of system 100 are particularlydescribed wherein the devices (e.g., the UEs 102 and the network device104) of system 100 are configured to communicate wireless signals usingone or more multi carrier modulation schemes, wherein data symbols canbe transmitted simultaneously over multiple frequency subcarriers (e.g.,OFDM, CP-OFDM, DFT-spread OFMD, UFMC, FMBC, etc.). The embodiments areapplicable to single carrier as well as to multicarrier (MC) or carrieraggregation (CA) operation of the UE. The term carrier aggregation (CA)is also called (e.g. interchangeably called) “multi-carrier system”,“multi-cell operation”, “multi-carrier operation”, “multi-carrier”transmission and/or reception. Note that some embodiments are alsoapplicable for Multi RAB (radio bearers) on some carriers (that is dataplus speech is simultaneously scheduled).

In various embodiments, system 100 can be configured to provide andemploy 5G wireless networking features and functionalities. 5G wirelesscommunication networks are expected to fulfill the demand ofexponentially increasing data traffic and to allow people and machinesto enjoy gigabit data rates with virtually zero latency. Compared to 4G,5G supports more diverse traffic scenarios. For example, in addition tothe various types of data communication between conventional UEs (e.g.,phones, smartphones, tablets, PCs, televisions, Internet enabledtelevisions, etc.) supported by 4G networks, 5G networks can be employedto support data communication between smart cars in association withdriverless car environments, as well as machine type communications(MTCs). Considering the drastic different communication needs of thesedifferent traffic scenarios, the ability to dynamically configurewaveform parameters based on traffic scenarios while retaining thebenefits of multi carrier modulation schemes (e.g., OFDM and relatedschemes) can provide a significant contribution to the highspeed/capacity and low latency demands of 5G networks. With waveformsthat split the bandwidth into several sub-bands, different types ofservices can be accommodated in different sub-bands with the mostsuitable waveform and numerology, leading to an improved spectrumutilization for 5G networks.

To meet the demand for data centric applications, features of proposed5G networks may comprise: increased peak bit rate (e.g., 20 Gbps),larger data volume per unit area (e.g., high system spectralefficiency—for example about 3.5 times that of spectral efficiency oflong term evolution (LTE) systems), high capacity that allows moredevice connectivity both concurrently and instantaneously, lowerbattery/power consumption (which reduces energy and consumption costs),better connectivity regardless of the geographic region in which a useris located, a larger numbers of devices, lower infrastructuraldevelopment costs, and higher reliability of the communications. Thus,5G networks may allow for: data rates of several tens of megabits persecond should be supported for tens of thousands of users, 1 gigabit persecond to be offered simultaneously to tens of workers on the sameoffice floor, for example; several hundreds of thousands of simultaneousconnections to be supported for massive sensor deployments; improvedcoverage, enhanced signaling efficiency; reduced latency compared toLTE.

The upcoming 5G access network may utilize higher frequencies (e.g., >6GHz) to aid in increasing capacity. Currently, much of the millimeterwave (mmWave) spectrum, the band of spectrum between 30 GHz and 300 GHzis underutilized. The millimeter waves have shorter wavelengths thatrange from 10 millimeters to 1 millimeter, and these mmWave signalsexperience severe path loss, penetration loss, and fading. However, theshorter wavelength at mmWave frequencies also allows more antennas to bepacked in the same physical dimension, which allows for large-scalespatial multiplexing and highly directional beamforming.

Performance can be improved if both the transmitter and the receiver areequipped with multiple antennas. Multi-antenna techniques cansignificantly increase the data rates and reliability of a wirelesscommunication system. The use of multiple input multiple output (MIMO)techniques, which was introduced in the third-generation partnershipproject (3GPP) and has been in use (including with LTE), is amulti-antenna technique that can improve the spectral efficiency oftransmissions, thereby significantly boosting the overall data carryingcapacity of wireless systems. The use of multiple-input multiple-output(MIMO) techniques can improve mmWave communications, and has been widelyrecognized a potentially important component for access networksoperating in higher frequencies. MIMO can be used for achievingdiversity gain, spatial multiplexing gain and beamforming gain. Forthese reasons, MIMO systems are an important part of the 3rd and 4thgeneration wireless systems, and are planned for use in 5G systems.

Referring now to FIG. 2, illustrated is an example schematic systemblock diagram of integrated access and backhaul links according to oneor more embodiments. For example, the network 200, as represented inFIG. 2 with integrated access and backhaul links, can allow a relay nodeto multiplex access and backhaul links in time, frequency, and/or space(e.g. beam-based operation). Thus, FIG. 2 illustrates a generic IABset-up comprising a core network 202, a centralized unit 204, a donordistributed unit 206, a relay distributed unit 208, and UEs 1021, 1022,1023. The donor distributed unit 206 (e.g., access point) can have awired backhaul with a protocol stack and can relay the user traffic forthe UEs 1021, 1022, 1023 across the IAB and backhaul link. Then therelay distributed unit 208 can take the backhaul link and convert itinto different strains for the connected UEs 1021, 1022, 1023. AlthoughFIG. 2 depicts a single hop (e.g., over the air), it should be notedthat multiple backhaul hops can occur in other embodiments.

The relays can have the same type of distributed unit structure that thegNode B has. For 5G, the protocol stack can be split, where some of thestack is centralized. For example, the PDCP layer and above can be atthe centralized unit 204, but in a real time application part of theprotocol stack, the radio link control (RLC), the medium access control(MAC), and the physical layer PHY can be co-located with the basestation wherein the system can comprise an F1 interface. In order to addrelaying, the F1 interface can be wireless so that the same structure ofthe donor distributed unit 206 can be kept.

Referring now to FIG. 3, illustrated is an example of RAN networkarchitecture 300 in accordance with various aspects and embodimentsdescribed herein. The network architecture 300 comprises a RANintelligent controller 302 (RIC) having a buffer control application 304(e.g., xAPP). The buffer control application 304 is communicativelyconnected to an application server 306 and congestion/flow control 308via an A1 interface 310. The A1 interface 310 allows network managementapplications in RIC 302, also referred to as RIC near-real time (RT), toreceive highly reliable data in a standardized format. For example,messages generated from artificial intelligent-enabled policies andmachine-learning based training models can be conveyed to RIC 302. Thecore algorithm of RIC 302 can be developed and owned by operators. Itprovides the capability to modify the RAN behaviors by deployment ofdifferent models optimized to individual operator policies andoptimization objectives.

In some embodiments, a distributed unit (DU) 314 and a central unit userplane (CU-UP) 318 has been specified by 3GPP. The DU 314 iscommunicatively connected to CU-UP) 318 via an application data link316. The buffers for DU and CU-UP can be controlled by the RIC 302 viaan E2 interface 312. The E2 interface 312 feeds data, including variousRAN measurements, to the RIC 302 to facilitate radio resourcemanagement, it is also the interface through which the RIC near-RT 302may initiate configuration commands directly to DU and CU-UP (e.g., torequest adjustments to buffer size). Each individual functional entitiesDU and CU-UP may be placed at different physical locations according tooperator requirements.

In some embodiments, a buffer management xApp 304 running on the RICwill monitor the RAN and the flow performance and dynamically tune theavailable policies through the E2 interface 312. The xApp 302 will runan algorithm to optimize the application performance. The per-flowrequirements of throughput, latency, or application burstcharacteristics are communicated to the xAPP 304 through the A1interface 310 the RIC 302. In some embodiments, The RIC 302 can performthese optimizations, not at a per-packet but, at the order of tens ofmilliseconds to hundreds of milliseconds. This time horizon is longenough to get aggregate RAN statistics to the RIC 302 and short enoughsuch that the RIC 302 can monitor any bursts in traffic and ensure lowlatency (order of tens of milliseconds).

Referring now to FIG. 4, illustrated is an example of a buffer controlalgorithm 400 that can facilitate optimizing congestion control usingradio access network (RAN) intelligent controller in accordance withvarious aspects and embodiments described herein. The buffer controlalgorithm is deployed in the RIC 302. Deploying the algorithm at RIC isbeneficial since RIC provides a flexible way to monitor per UEperformance and manage RAN parameters. The RIC also has knowledge of allflows through an eNB/gNB to make globally optimal decisions. Atoperation 402, the buffer control algorithm measures the throughput andper-packet delay of each flow. At operation 404, the buffer controlalgorithm periodically performs small experiments by changing the buffersizes or queuing policy at a flow. At operation 406, the results ofthese experiments will be evaluated to see if the flow meets itsperformance requirements of throughput and latency. At operation 410,based on meeting the performance requirements and using various machinelearning techniques, the algorithm can explore the state space andarrive at the optimal solution for each flow to make any adjustments.

FIG. 5 illustrates a block diagram of an example, non-limiting system500 that facilitates flexible buffer management for optimizingcongestion control using radio access network (RAN) intelligentcontroller in accordance with one or more embodiments described herein.Repetitive description of like elements employed in respectiveembodiments is omitted for sake of brevity. According to someembodiments, the system 500 can comprise a small cell having a RANscheduler 502. In some embodiments, the RAN scheduler 502 can alsoinclude or otherwise be associated with a memory 504, a processor 506that executes computer executable components stored in a memory 504. TheRAN scheduler 502 can further include a system bus 508 that can couplevarious components including, but not limited to, a monitor component510, a receiving component 512, and an adjustment component 514.

Aspects of systems (e.g., the RAN scheduler 502 and the like),apparatuses, or processes explained in this disclosure can constitutemachine-executable component(s) embodied within machine(s), e.g.,embodied in one or more computer readable mediums (or media) associatedwith one or more machines. Such component(s), when executed by the oneor more machines, e.g., computer(s), computing device(s), virtualmachine(s), etc. can cause the machine(s) to perform the operationsdescribed.

It should be appreciated that the embodiments of the subject disclosuredepicted in various figures disclosed herein are for illustration only,and as such, the architecture of such embodiments are not limited to thesystems, devices, and/or components depicted therein. For example, insome embodiments, the RAN scheduler 502 can comprise various computerand/or computing-based elements described herein with reference tooperating environment 1000 and FIG. 10. In several embodiments, suchcomputer and/or computing-based elements can be used in connection withimplementing one or more of the systems, devices, and/or componentsshown and described in connection with FIG. 5 or other figures disclosedherein.

According to several embodiments, the memory 504 can store one or morecomputer and/or machine readable, writable, and/or executable componentsand/or instructions that, when executed by processor 506, can facilitateperformance of operations defined by the executable component(s) and/orinstruction(s). For example, the memory 504 can store computer and/ormachine readable, writable, and/or executable components and/orinstructions that, when executed by the processor 506, can facilitateexecution of the various functions described herein relating to themonitor component 510, the receiving component 512, and the adjustmentcomponent 514.

In several embodiments, the memory 504 can comprise volatile memory(e.g., random access memory (RAM), static RAM (SRAM), dynamic RAM(DRAM), etc.) and/or non-volatile memory (e.g., read only memory (ROM),programmable ROM (PROM), electrically programmable ROM (EPROM),electrically erasable programmable ROM (EEPROM), etc.) that can employone or more memory architectures. Further examples of memory 504 aredescribed below with reference to system memory 1006 and FIG. 10. Suchexamples of memory 504 can be employed to implement any embodiments ofthe subject disclosure.

According to some embodiments, the processor 506 can comprise one ormore types of processors and/or electronic circuitry that can implementone or more computer and/or machine readable, writable, and/orexecutable components and/or instructions that can be stored on thememory 504. For example, the processor 506 can perform variousoperations that can be specified by such computer and/or machinereadable, writable, and/or executable components and/or instructionsincluding, but not limited to, logic, control, input/output (I/O),arithmetic, and/or the like. In some embodiments, processor 506 cancomprise one or more central processing unit, multi-core processor,microprocessor, dual microprocessors, microcontroller, System on a Chip(SOC), array processor, vector processor, and/or another type ofprocessor.

In some embodiments, the processor 506, the memory 504, the monitorcomponent 510, the receiving component 512, and the adjustment component514 can be communicatively, electrically, and/or operatively coupled toone another via the system bus 508 to perform functions of the RANscheduler 502, and/or any components coupled therewith. In severalembodiments, the system bus 508 can comprise one or more memory bus,memory controller, peripheral bus, external bus, local bus, and/oranother type of bus that can employ various bus architectures.

In several embodiments, the RAN scheduler 502 can comprise one or morecomputer and/or machine readable, writable, and/or executable componentsand/or instructions that, when executed by the processor 506, canfacilitate performance of operations defined by such component(s) and/orinstruction(s). Further, in numerous embodiments, any componentassociated with the RAN scheduler 502, as described herein with orwithout reference to the various figures of the subject disclosure, cancomprise one or more computer and/or machine readable, writable, and/orexecutable components and/or instructions that, when executed by theprocessor 506, can facilitate performance of operations defined by suchcomponent(s) and/or instruction(s). For example, the monitor component510, and/or any other components associated with the RAN scheduler 502(e.g., communicatively, electronically, and/or operatively coupled withand/or employed by RAN scheduler 502), can comprise such computer and/ormachine readable, writable, and/or executable component(s) and/orinstruction(s). Consequently, according to numerous embodiments, the RANscheduler 502 and/or any components associated therewith, can employ theprocessor 506 to execute such computer and/or machine readable,writable, and/or executable component(s) and/or instruction(s) tofacilitate performance of one or more operations described herein withreference to the RAN scheduler 502 and/or any such components associatedtherewith.

In some embodiments, the RAN scheduler 502 can facilitate performance ofoperations related to and/or executed by the components of RAN scheduler502, for example, the processor 506, the memory 504, the monitorcomponent 510, the receiving component 512, and the adjustment component514. For example, as described in detail below, the RAN scheduler 502can facilitate: monitoring (e.g., by the monitor component 510) aperformance of a communication traffic flow using a group of bufferparameters of a network node; receiving (e.g., the receiving component512) performance values for requested performance characteristics of theperformance of the communication traffic flow via a first interface; andbased on performance values, adjusting (e.g., by the adjusting component514), via a second interface, a buffer parameter of the group of bufferparameters based on an adjustment value.

In some embodiments, the monitor component 510, can comprise one or moreprocessors, memory, and electrical circuitry. The monitor component 510monitors a communication traffic flow performance using a group ofbuffer parameters of a network node. In some embodiments, the eNB/gNBbuffer management xApp running on the RIC will monitor the RAN and theflow performance and dynamically tune the available policies through theE2 interface. In some embodiments, the flow performance can be measuredby packet drop rates, RTT (round trip time), or a congestion marker tomake control decisions. The monitor component 510 can use an intelligentbuffer management through the RIC to influence the behavior ofcongestion control algorithms.

In some embodiments, the receive component 512, can comprise one or moreprocessors, memory, and electrical circuitry. In some embodiments, thereceive component 512 can receive the required performancecharacteristics of the communication traffic flow performance via aninterface. For example, the receive component 512 can receive theper-flow requirements of throughput, latency requirements, orapplication burst characteristics. These requirements can becommunicated to the xAPP of the RIC through the A1 interface.

In some embodiments, the adjustment component 514, can comprise one ormore processors, memory, and electrical circuitry. The adjustmentcomponent 514, based on performance values, adjusting a buffer parameterof a network device based on an adjustment value (e.g., value indicatinghow much the buffer size should be adjusted or data for how the policiesshould be changed). The xApp will run an algorithm to optimize theapplication performance (e.g., the algorithm can explore the state spaceand arrive at the optimal solution for each flow). The buffer controlalgorithm measures the throughput and per-packet delay of each flow. Thealgorithm periodically performs small experiments by adjusting thebuffer sizes or queuing policy at a flow. Tuning the schedulingalgorithm is performed at a slower time scale. The results of theseexperiments will be evaluated to see if the flow meets its performancerequirements of throughput and latency.

FIG. 6 depicts a diagram of an example, non-limiting computerimplemented method that facilitates flexible buffer management foroptimizing congestion control using radio access network (RAN)intelligent controller in accordance with one or more embodimentsdescribed herein. In some examples, flow diagram 600 can be implementedby operating environment 1000 described below. It can be appreciatedthat the operations of flow diagram 600 can be implemented in adifferent order than is depicted.

In non-limiting example embodiments, a computing device (or system)(e.g., computer 1004) is provided, the device or system comprising oneor more processors and one or more memories that stores executableinstructions that, when executed by the one or more processors, canfacilitate performance of the operations as described herein, includingthe non-limiting methods as illustrated in the flow diagrams of FIG. 6.

Operation 602 depicts monitoring, by a device comprising a processor, acommunication traffic flow performance using a group of bufferparameters of a network node device of a wireless network. In someembodiments, the eNB/gNB buffer management xApp running on the RIC willmonitor the RAN and the flow performance and dynamically tune theavailable policies through the E2 interface. Operation 604 depictsdetermining if the traffic flow needs adjustment. If the traffic flowneeds adjustment, perform Operation 606. Otherwise, continue monitoring.Operation 606 depicts receiving, by the device, required performancecharacteristics of the communication traffic flow performance via aninterface (e.g., the per-flow requirements of throughput, latency, orapplication burst characteristics are communicated to the xAPP of theRIC through the A1 interface). Operation 608 depicts based onperformance values, adjusting, by the device, a buffer parameter of anetwork node device of the wireless network based on an adjustmentvalue. The xApp will run an algorithm (described below) to optimize theapplication performance (e.g., the algorithm can explore the state spaceand arrive at the optimal solution for each flow). The buffer controlalgorithm measures the throughput and per-packet delay of each flow. Thealgorithm periodically performs small experiments by adjusting thebuffer sizes or queuing policy at a flow. Tuning the schedulingalgorithm is performed at a slower time scale. The results of theseexperiments will be evaluated to see if the flow meets its performancerequirements of throughput and latency.

FIG. 7 depicts a diagram of an example, non-limiting computerimplemented method that facilitates flexible buffer management foroptimizing congestion control using radio access network (RAN)intelligent controller in accordance with one or more embodimentsdescribed herein. In some examples, flow diagram 700 can be implementedby operating environment 1000 described below. It can be appreciatedthat the operations of flow diagram 700 can be implemented in adifferent order than is depicted.

In non-limiting example embodiments, a computing device (or system)(e.g., computer 1004) is provided, the device or system comprising oneor more processors and one or more memories that stores executableinstructions that, when executed by the one or more processors, canfacilitate performance of the operations as described herein, includingthe non-limiting methods as illustrated in the flow diagrams of FIG. 7.

Operation 702 depicts monitoring, by a device comprising a processor, acommunication traffic flow performance using a group of bufferparameters of a network node device of a wireless network. In someembodiments, the eNB/gNB buffer management xApp running on the RIC willmonitor the RAN and the flow performance and dynamically tune theavailable policies through the E2 interface. Operation 704 depictsdetermining if the traffic flow needs adjustment. If the traffic flowneeds adjustment, perform Operation 706. Otherwise, continue monitoring.Operation 706 depicts receiving, by the device, required performancecharacteristics of the communication traffic flow performance via aninterface (e.g., the per-flow requirements of throughput, latency, orapplication burst characteristics are communicated to the xAPP of theRIC through the A1 interface). Operation 708 depicts based onperformance values, adjusting, by the device, a buffer parameter of anetwork node device of the wireless network based on an adjustmentvalue. The xApp will run an algorithm (described below) to optimize theapplication performance (e.g., the algorithm can explore the state spaceand arrive at the optimal solution for each flow). The buffer controlalgorithm measures the throughput and per-packet delay of each flow. Thealgorithm periodically performs small experiments by adjusting thebuffer sizes or queuing policy at a flow. Tuning the schedulingalgorithm is performed at a slower time scale. The results of theseexperiments will be evaluated to see if the flow meets its performancerequirements of throughput and latency. Operation 710 depicts based onthe required performance characteristics, determining, by the device,that the buffer parameter is available for adjustment to satisfy thecommunication traffic flow performance.

FIG. 8 depicts a diagram of an example, non-limiting computerimplemented method that facilitates flexible buffer management foroptimizing congestion control using radio access network (RAN)intelligent controller in accordance with one or more embodimentsdescribed herein. In some examples, flow diagram 800 can be implementedby operating environment 1000 described below. It can be appreciatedthat the operations of flow diagram 800 can be implemented in adifferent order than is depicted.

In non-limiting example embodiments, a computing device (or system)(e.g., computer 1004) is provided, the device or system comprising oneor more processors and one or more memories that stores executableinstructions that, when executed by the one or more processors, canfacilitate performance of the operations as described herein, includingthe non-limiting methods as illustrated in the flow diagrams of FIG. 8.

Operation 802 depicts monitoring, by a device comprising a processor, acommunication traffic flow performance using a group of bufferparameters of a network node device of a wireless network. In someembodiments, the eNB/gNB buffer management xApp running on the RIC willmonitor the RAN and the flow performance and dynamically tune theavailable policies through the E2 interface. Operation 804 depictsdetermining if the traffic flow needs adjustment. If the traffic flowneeds adjustment, perform Operation 806. Otherwise, continue monitoring.Operation 806 depicts receiving, by the device, required performancecharacteristics of the communication traffic flow performance via aninterface (e.g., the per-flow requirements of throughput, latency, orapplication burst characteristics are communicated to the xAPP of theRIC through the A1 interface). Operation 808 depicts based onperformance values, adjusting, by the device, a buffer parameter of anetwork node device of the wireless network based on an adjustmentvalue. The xApp will run an algorithm (described below) to optimize theapplication performance (e.g., the algorithm can explore the state spaceand arrive at the optimal solution for each flow). The buffer controlalgorithm measures the throughput and per-packet delay of each flow. Thealgorithm periodically performs small experiments by adjusting thebuffer sizes or queuing policy at a flow. Tuning the schedulingalgorithm is performed at a slower time scale. The results of theseexperiments will be evaluated to see if the flow meets its performancerequirements of throughput and latency. Operation 810 depictsperforming, by the device, a series of adjustments to the group ofbuffer parameters to identify the buffer parameter and the adjustmentvalue.

FIG. 9 depicts a diagram of an example, non-limiting computerimplemented method that facilitates flexible buffer management foroptimizing congestion control using radio access network (RAN)intelligent controller in accordance with one or more embodimentsdescribed herein. In some examples, flow diagram 900 can be implementedby operating environment 1000 described below. It can be appreciatedthat the operations of flow diagram 900 can be implemented in adifferent order than is depicted.

In non-limiting example embodiments, a computing device (or system)(e.g., computer 1004) is provided, the device or system comprising oneor more processors and one or more memories that stores executableinstructions that, when executed by the one or more processors, canfacilitate performance of the operations as described herein, includingthe non-limiting methods as illustrated in the flow diagrams of FIG. 9.

Operation 902 depicts monitoring, by a device comprising a processor, acommunication traffic flow performance using a group of bufferparameters of a network node device of a wireless network. In someembodiments, the eNB/gNB buffer management xApp running on the RIC willmonitor the RAN and the flow performance and dynamically tune theavailable policies through the E2 interface. Operation 904 depictsdetermining if the traffic flow needs adjustment. If the traffic flowneeds adjustment, perform Operation 906. Otherwise, continue monitoring.Operation 906 depicts receiving, by the device, required performancecharacteristics of the communication traffic flow performance via aninterface (e.g., the per-flow requirements of throughput, latency, orapplication burst characteristics are communicated to the xAPP of theRIC through the A1 interface). Operation 908 depicts based onperformance values, adjusting, by the device, a buffer parameter of anetwork node device of the wireless network based on an adjustmentvalue. The xApp will run an algorithm to optimize the applicationperformance (e.g., the algorithm can explore the state space and arriveat the optimal solution for each flow). The buffer control algorithmmeasures the throughput and per-packet delay of each flow. The algorithmperiodically performs small experiments by adjusting the buffer sizes orqueuing policy at a flow. Tuning the scheduling algorithm is performedat a slower time scale. The results of these experiments will beevaluated to see if the flow meets its performance requirements ofthroughput and latency. Operation 910 depicts performing, by the device,a series of adjustments to the group of buffer parameters to identifythe buffer parameter and the adjustment value. Operation 912 depictsselecting, by the device, the buffer parameter and the adjustment valuebased on analyzing impact on the communication traffic flow performance.

Referring now to FIG. 10, illustrated is an example block diagram of anexample computer 1000 operable to engage in a system architecture thatfacilitates wireless communications according to one or more embodimentsdescribed herein. The computer 1000 can provide networking andcommunication capabilities between a wired or wireless communicationnetwork and a server and/or communication device.

In order to provide additional context for various embodiments describedherein, FIG. 10 and the following discussion are intended to provide abrief, general description of a suitable computing environment 1000 inwhich the various embodiments of the embodiment described herein can beimplemented. While the embodiments have been described above in thegeneral context of computer-executable instructions that can run on oneor more computers, those skilled in the art will recognize that theembodiments can be also implemented in combination with other programmodules and/or as a combination of hardware and software.

Generally, program modules include routines, programs, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. Moreover, those skilled in the art will appreciatethat the methods can be practiced with other computer systemconfigurations, including single-processor or multiprocessor computersystems, minicomputers, mainframe computers, Internet of Things (IoT)devices, distributed computing systems, as well as personal computers,hand-held computing devices, microprocessor-based or programmableconsumer electronics, and the like, each of which can be operativelycoupled to one or more associated devices.

The illustrated embodiments of the embodiments herein can be alsopracticed in distributed computing environments where certain tasks areperformed by remote processing devices that are linked through acommunications network. In a distributed computing environment, programmodules can be located in both local and remote memory storage devices.

Computing devices typically include a variety of media, which caninclude computer-readable storage media, machine-readable storage media,and/or communications media, which two terms are used herein differentlyfrom one another as follows. Computer-readable storage media ormachine-readable storage media can be any available storage media thatcan be accessed by the computer and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media or machine-readablestorage media can be implemented in connection with any method ortechnology for storage of information such as computer-readable ormachine-readable instructions, program modules, structured data orunstructured data.

Computer-readable storage media can include, but are not limited to,random access memory (RAM), read only memory (ROM), electricallyerasable programmable read only memory (EEPROM), flash memory or othermemory technology, compact disk read only memory (CD-ROM), digitalversatile disk (DVD), Blu-ray disc (BD) or other optical disk storage,magnetic cassettes, magnetic tape, magnetic disk storage or othermagnetic storage devices, solid state drives or other solid statestorage devices, or other tangible and/or non-transitory media which canbe used to store desired information. In this regard, the terms“tangible” or “non-transitory” herein as applied to storage, memory orcomputer-readable media, are to be understood to exclude onlypropagating transitory signals per se as modifiers and do not relinquishrights to all standard storage, memory or computer-readable media thatare not only propagating transitory signals per se.

Computer-readable storage media can be accessed by one or more local orremote computing devices, e.g., via access requests, queries or otherdata retrieval protocols, for a variety of operations with respect tothe information stored by the medium.

Communications media typically embody computer-readable instructions,data structures, program modules or other structured or unstructureddata in a data signal such as a modulated data signal, e.g., a carrierwave or other transport mechanism, and includes any information deliveryor transport media. The term “modulated data signal” or signals refersto a signal that has one or more of its characteristics set or changedin such a manner as to encode information in one or more signals. By wayof example, and not limitation, communication media include wired media,such as a wired network or direct-wired connection, and wireless mediasuch as acoustic, RF, infrared and other wireless media.

With reference again to FIG. 10, the example environment 1000 forimplementing various embodiments of the aspects described hereinincludes a computer 1002, the computer 1002 including a processing unit1004, a system memory 1006 and a system bus 1008. The system bus 1008couples system components including, but not limited to, the systemmemory 1006 to the processing unit 1004. The processing unit 1004 can beany of various commercially available processors. Dual microprocessorsand other multi-processor architectures can also be employed as theprocessing unit 1004.

The system bus 1008 can be any of several types of bus structure thatcan further interconnect to a memory bus (with or without a memorycontroller), a peripheral bus, and a local bus using any of a variety ofcommercially available bus architectures. The system memory 1006includes ROM 1010 and RAM 1012. A basic input/output system (BIOS) canbe stored in a non-volatile memory such as ROM, erasable programmableread only memory (EPROM), EEPROM, which BIOS contains the basic routinesthat help to transfer information between elements within the computer1002, such as during startup. The RAM 1012 can also include a high-speedRAM such as static RAM for caching data.

The computer 1002 further includes an internal hard disk drive (HDD)1014 (e.g., EIDE, SATA), one or more external storage devices 1016(e.g., a magnetic floppy disk drive (FDD) 1016, a memory stick or flashdrive reader, a memory card reader, etc.) and an optical disk drive 1020(e.g., which can read or write from a CD-ROM disc, a DVD, a BD, etc.).While the internal HDD 1014 is illustrated as located within thecomputer 1002, the internal HDD 1014 can also be configured for externaluse in a suitable chassis (not shown). Additionally, while not shown inenvironment 1000, a solid state drive (SSD) could be used in additionto, or in place of, an HDD 1014. The HDD 1014, external storagedevice(s) 1016 and optical disk drive 1020 can be connected to thesystem bus 1008 by an HDD interface 1024, an external storage interface1026 and an optical drive interface 1028, respectively. The interface1024 for external drive implementations can include at least one or bothof Universal Serial Bus (USB) and Institute of Electrical andElectronics Engineers (IEEE) 1394 interface technologies. Other externaldrive connection technologies are within contemplation of theembodiments described herein.

The drives and their associated computer-readable storage media providenonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For the computer 1002, the drives andstorage media accommodate the storage of any data in a suitable digitalformat. Although the description of computer-readable storage mediaabove refers to respective types of storage devices, it should beappreciated by those skilled in the art that other types of storagemedia which are readable by a computer, whether presently existing ordeveloped in the future, could also be used in the example operatingenvironment, and further, that any such storage media can containcomputer-executable instructions for performing the methods describedherein.

A number of program modules can be stored in the drives and RAM 1012,including an operating system 1030, one or more application programs1032, other program modules 1034 and program data 1036. All or portionsof the operating system, applications, modules, and/or data can also becached in the RAM 1012. The systems and methods described herein can beimplemented utilizing various commercially available operating systemsor combinations of operating systems.

Computer 1002 can optionally comprise emulation technologies. Forexample, a hypervisor (not shown) or other intermediary can emulate ahardware environment for operating system 1030, and the emulatedhardware can optionally be different from the hardware illustrated inFIG. 10. In such an embodiment, operating system 1030 can comprise onevirtual machine (VM) of multiple VMs hosted at computer 1002.Furthermore, operating system 1030 can provide runtime environments,such as the Java runtime environment or the .NET framework, forapplications 1032. Runtime environments are consistent executionenvironments that allow applications 1032 to run on any operating systemthat includes the runtime environment. Similarly, operating system 1030can support containers, and applications 1032 can be in the form ofcontainers, which are lightweight, standalone, executable packages ofsoftware that include, e.g., code, runtime, system tools, systemlibraries and settings for an application.

Further, computer 1002 can be enable with a security module, such as atrusted processing module (TPM). For instance with a TPM, bootcomponents hash next in time boot components, and wait for a match ofresults to secured values, before loading a next boot component. Thisprocess can take place at any layer in the code execution stack ofcomputer 1002, e.g., applied at the application execution level or atthe operating system (OS) kernel level, thereby enabling security at anylevel of code execution.

A user can enter commands and information into the computer 1002 throughone or more wired/wireless input devices, e.g., a keyboard 1038, a touchscreen 1040, and a pointing device, such as a mouse 1042. Other inputdevices (not shown) can include a microphone, an infrared (IR) remotecontrol, a radio frequency (RF) remote control, or other remote control,a joystick, a virtual reality controller and/or virtual reality headset,a game pad, a stylus pen, an image input device, e.g., camera(s), agesture sensor input device, a vision movement sensor input device, anemotion or facial detection device, a biometric input device, e.g.,fingerprint or iris scanner, or the like. These and other input devicesare often connected to the processing unit 1004 through an input deviceinterface 1044 that can be coupled to the system bus 1008, but can beconnected by other interfaces, such as a parallel port, an IEEE 1394serial port, a game port, a USB port, an IR interface, a BLUETOOTH®interface, etc.

A monitor 1046 or other type of display device can be also connected tothe system bus 1008 via an interface, such as a video adapter 1048. Inaddition to the monitor 1046, a computer typically includes otherperipheral output devices (not shown), such as speakers, printers, etc.

The computer 1002 can operate in a networked environment using logicalconnections via wired and/or wireless communications to one or moreremote computers, such as a remote computer(s) 1050. The remotecomputer(s) 1050 can be a workstation, a server computer, a router, apersonal computer, portable computer, microprocessor-based entertainmentappliance, a peer device or other common network node, and typicallyincludes many or all of the elements described relative to the computer1002, although, for purposes of brevity, only a memory/storage device1052 is illustrated. The logical connections depicted includewired/wireless connectivity to a local area network (LAN) 1054 and/orlarger networks, e.g., a wide area network (WAN) 1056. Such LAN and WANnetworking environments are commonplace in offices and companies, andfacilitate enterprise-wide computer networks, such as intranets, all ofwhich can connect to a global communications network, e.g., theInternet.

When used in a LAN networking environment, the computer 1002 can beconnected to the local network 1054 through a wired and/or wirelesscommunication network interface or adapter 1058. The adapter 1058 canfacilitate wired or wireless communication to the LAN 1054, which canalso include a wireless access point (AP) disposed thereon forcommunicating with the adapter 1058 in a wireless mode.

When used in a WAN networking environment, the computer 1002 can includea modem 1060 or can be connected to a communications server on the WAN1056 via other means for establishing communications over the WAN 1056,such as by way of the Internet. The modem 1060, which can be internal orexternal and a wired or wireless device, can be connected to the systembus 1008 via the input device interface 1044. In a networkedenvironment, program modules depicted relative to the computer 1002 orportions thereof, can be stored in the remote memory/storage device1052. It will be appreciated that the network connections shown areexample and other means of establishing a communications link betweenthe computers can be used.

When used in either a LAN or WAN networking environment, the computer1002 can access cloud storage systems or other network-based storagesystems in addition to, or in place of, external storage devices 1016 asdescribed above. Generally, a connection between the computer 1002 and acloud storage system can be established over a LAN 1054 or WAN 1056e.g., by the adapter 1058 or modem 1060, respectively. Upon connectingthe computer 1002 to an associated cloud storage system, the externalstorage interface 1026 can, with the aid of the adapter 1058 and/ormodem 1060, manage storage provided by the cloud storage system as itwould other types of external storage. For instance, the externalstorage interface 1026 can be configured to provide access to cloudstorage sources as if those sources were physically connected to thecomputer 1002.

The computer 1002 can be operable to communicate with any wirelessdevices or entities operatively disposed in wireless communication,e.g., a printer, scanner, desktop and/or portable computer, portabledata assistant, communications satellite, any piece of equipment orlocation associated with a wirelessly detectable tag (e.g., a kiosk,news stand, store shelf, etc.), and telephone. This can include WirelessFidelity (Wi-Fi) and BLUETOOTH® wireless technologies. Thus, thecommunication can be a predefined structure as with a conventionalnetwork or simply an ad hoc communication between at least two devices.

The above description of illustrated embodiments of the subjectdisclosure, including what is described in the Abstract, is not intendedto be exhaustive or to limit the disclosed embodiments to the preciseforms disclosed. While specific embodiments and examples are describedherein for illustrative purposes, various modifications are possiblethat are considered within the scope of such embodiments and examples,as those skilled in the relevant art can recognize.

In this regard, while the disclosed subject matter has been described inconnection with various embodiments and corresponding Figures, whereapplicable, it is to be understood that other similar embodiments can beused or modifications and additions can be made to the describedembodiments for performing the same, similar, alternative, or substitutefunction of the disclosed subject matter without deviating therefrom.Therefore, the disclosed subject matter should not be limited to anysingle embodiment described herein, but rather should be construed inbreadth and scope in accordance with the appended claims below.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit (ASIC), a digitalsignal processor (DSP), a field programmable gate array (FPGA), aprogrammable logic controller (PLC), a complex programmable logic device(CPLD), a discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. Processors can exploit nano-scale architectures suchas, but not limited to, molecular and quantum-dot based transistors,switches and gates, in order to optimize space usage or enhanceperformance of user equipment. A processor may also be implemented as acombination of computing processing units.

In the subject specification, terms such as “store,” “storage,” “datastore,” data storage,” “database,” and substantially any otherinformation storage component relevant to operation and functionality ofa component, refer to “memory components,” or entities embodied in a“memory” or components comprising the memory. It will be appreciatedthat the memory components described herein can be either volatilememory or nonvolatile memory, or can include both volatile andnonvolatile memory.

As used in this application, the terms “component,” “system,”“platform,” “layer,” “selector,” “interface,” and the like are intendedto refer to a computer-related entity or an entity related to anoperational apparatus with one or more specific functionalities, whereinthe entity can be either hardware, a combination of hardware andsoftware, software, or software in execution. As an example, a componentmay be, but is not limited to being, a process running on a processor, aprocessor, an object, an executable, a thread of execution, a program,and/or a computer. By way of illustration and not limitation, both anapplication running on a server and the server can be a component. Oneor more components may reside within a process and/or thread ofexecution and a component may be localized on one computer and/ordistributed between two or more computers. In addition, these componentscan execute from various computer readable media, device readablestorage devices, or machine readable media having various datastructures stored thereon. The components may communicate via localand/or remote processes such as in accordance with a signal having oneor more data packets (e.g., data from one component interacting withanother component in a local system, distributed system, and/or across anetwork such as the Internet with other systems via the signal). Asanother example, a component can be an apparatus with specificfunctionality provided by mechanical parts operated by electric orelectronic circuitry, which is operated by a software or firmwareapplication executed by a processor, wherein the processor can beinternal or external to the apparatus and executes at least a part ofthe software or firmware application. As yet another example, acomponent can be an apparatus that provides specific functionalitythrough electronic components without mechanical parts, the electroniccomponents can include a processor therein to execute software orfirmware that confers at least in part the functionality of theelectronic components.

In addition, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom context, “X employs A or B” is intended to mean any of the naturalinclusive permutations. That is, if X employs A; X employs B; or Xemploys both A and B, then “X employs A or B” is satisfied under any ofthe foregoing instances. Moreover, articles “a” and “an” as used in thesubject specification and annexed drawings should generally be construedto mean “one or more” unless specified otherwise or clear from contextto be directed to a singular form.

Moreover, terms like “user equipment (UE),” “mobile station,” “mobile,”subscriber station,” “subscriber equipment,” “access terminal,”“terminal,” “handset,” and similar terminology, refer to a wirelessdevice utilized by a subscriber or user of a wireless communicationservice to receive or convey data, control, voice, video, sound, gaming,or substantially any data-stream or signaling-stream. The foregoingterms are utilized interchangeably in the subject specification andrelated drawings. Likewise, the terms “access point (AP),” “basestation,” “NodeB,” “evolved Node B (eNodeB),” “home Node B (HNB),” “homeaccess point (HAP),” “cell device,” “sector,” “cell,” “relay device,”“node,” “point,” and the like, are utilized interchangeably in thesubject application, and refer to a wireless network component orappliance that serves and receives data, control, voice, video, sound,gaming, or substantially any data-stream or signaling-stream to and froma set of subscriber stations or provider enabled devices. Data andsignaling streams can include packetized or frame-based flows.

Additionally, the terms “core-network”, “core”, “core carrier network”,“carrier-side”, or similar terms can refer to components of atelecommunications network that typically provides some or all ofaggregation, authentication, call control and switching, charging,service invocation, or gateways. Aggregation can refer to the highestlevel of aggregation in a service provider network wherein the nextlevel in the hierarchy under the core nodes is the distribution networksand then the edge networks. UEs do not normally connect directly to thecore networks of a large service provider but can be routed to the coreby way of a switch or radio area network. Authentication can refer todeterminations regarding whether the user requesting a service from thetelecom network is authorized to do so within this network or not. Callcontrol and switching can refer determinations related to the futurecourse of a call stream across carrier equipment based on the callsignal processing. Charging can be related to the collation andprocessing of charging data generated by various network nodes. Twocommon types of charging mechanisms found in present day networks can beprepaid charging and postpaid charging. Service invocation can occurbased on some explicit action (e.g. call transfer) or implicitly (e.g.,call waiting). It is to be noted that service “execution” may or may notbe a core network functionality as third party network/nodes may takepart in actual service execution. A gateway can be present in the corenetwork to access other networks. Gateway functionality can be dependenton the type of the interface with another network.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,”“prosumer,” “agent,” and the like are employed interchangeablythroughout the subject specification, unless context warrants particulardistinction(s) among the terms. It should be appreciated that such termscan refer to human entities or automated components (e.g., supportedthrough artificial intelligence, as through a capacity to makeinferences based on complex mathematical formalisms), that can providesimulated vision, sound recognition and so forth.

Aspects, features, or advantages of the subject matter can be exploitedin substantially any, or any, wired, broadcast, wirelesstelecommunication, radio technology or network, or combinations thereof.Non-limiting examples of such technologies or networks include Geocasttechnology; broadcast technologies (e.g., sub-Hz, ELF, VLF, LF, MF, HF,VHF, UHF, SHF, THz broadcasts, etc.); Ethernet; X.25; powerline-typenetworking (e.g., PowerLine AV Ethernet, etc.); femto-cell technology;Wi-Fi; Worldwide Interoperability for Microwave Access (WiMAX); EnhancedGeneral Packet Radio Service (Enhanced GPRS); Third GenerationPartnership Project (3GPP or 3G) Long Term Evolution (LTE); 3GPPUniversal Mobile Telecommunications System (UMTS) or 3GPP UMTS; ThirdGeneration Partnership Project 2 (3GPP2) Ultra Mobile Broadband (UMB);High Speed Packet Access (HSPA); High Speed Downlink Packet Access(HSDPA); High Speed Uplink Packet Access (HSUPA); GSM Enhanced DataRates for GSM Evolution (EDGE) Radio Access Network (RAN) or GERAN; UMTSTerrestrial Radio Access Network (UTRAN); or LTE Advanced.

What has been described above includes examples of systems and methodsillustrative of the disclosed subject matter. It is, of course, notpossible to describe every combination of components or methods herein.One of ordinary skill in the art may recognize that many furthercombinations and permutations of the disclosure are possible.Furthermore, to the extent that the terms “includes,” “has,”“possesses,” and the like are used in the detailed description, claims,appendices and drawings such terms are intended to be inclusive in amanner similar to the term “comprising” as “comprising” is interpretedwhen employed as a transitional word in a claim.

While the various embodiments are susceptible to various modificationsand alternative constructions, certain illustrated implementationsthereof are shown in the drawings and have been described above indetail. It should be understood, however, that there is no intention tolimit the various embodiments to the specific forms disclosed, but onthe contrary, the intention is to cover all modifications, alternativeconstructions, and equivalents falling within the spirit and scope ofthe various embodiments.

In addition to the various implementations described herein, it is to beunderstood that other similar implementations can be used ormodifications and additions can be made to the describedimplementation(s) for performing the same or equivalent function of thecorresponding implementation(s) without deviating therefrom. Stillfurther, multiple processing chips or multiple devices can share theperformance of one or more functions described herein, and similarly,storage can be effected across a plurality of devices. Accordingly, thevarious embodiments are not to be limited to any single implementation,but rather are to be construed in breadth, spirit and scope inaccordance with the appended claims.

What is claimed is:
 1. A system, comprising: a processor; and a memorythat stores executable instructions that, when executed by theprocessor, facilitate performance of operations, comprising: monitoringa performance of a communication traffic flow, wherein the communicationtraffic flow is adjustable using a group of radio access network nodebuffer parameters; receiving performance values that indicate requestedperformance characteristics for the communication traffic flow; andadjusting a radio access network node buffer parameter of the group ofradio access network node buffer parameters based on a performance valueof the performance values.
 2. The system of claim 1, wherein theoperations further comprise: determining that the radio access networknode buffer parameter is available for adjustment to satisfy therequested performance characteristics.
 3. The system of claim 2, whereinthe operations further comprise: performing adjustments to the group ofradio access network node buffer parameters; and analyzing impact of theadjustments on the performance of the communication traffic flow.
 4. Thesystem of claim 1, wherein adjusting the radio access network nodebuffer parameter comprises modifying the radio access network nodebuffer parameter based on a policy of the radio access network node. 5.The system of claim 1, wherein the policy of the radio access networknode comprises at least one of a queuing policy and a scheduling policy.6. The system of claim 1, wherein adjusting the radio access networknode buffer parameter comprises modifying a number of droppable packets.7. The system of claim 1, wherein adjusting the radio access networknode buffer parameter comprises changing a buffer size.
 8. The system ofclaim 1, wherein the requested performance characteristics comprise atleast one of a throughput characteristic associated with thecommunication traffic flow, a latency characteristic associated with thecommunication traffic flow, or an application burst characteristicassociated with the communication traffic flow.
 9. The system of claim1, wherein the operations further comprise: in response to a handoverbeing requested, adjusting a buffer size of a buffer used by the radioaccess network node.
 10. A method, comprising: monitoring, by a devicecomprising a processor, performance of a communication traffic flow,wherein a group of buffer parameters of a buffer at a radio accessnetwork node are adjustable in order to adjust the communication trafficflow; receiving, by the device, target performance characteristics to beapplicable to the communication traffic flow performance; and adjusting,by the device, a buffer parameter of the group of buffer parametersbased on an adjustment value determined from the performance of thecommunication traffic flow and the target performance characteristics.11. The method of claim 10, further comprising: determining, by thedevice, that the buffer parameter is available for adjustment to satisfythe target performance characteristics.
 12. The method of claim 10,further comprising: performing, by the device, a series of adjustmentsto the group of buffer parameters; and analyzing impact of the series ofadjustments on the performance of the communication traffic flow. 13.The method of claim 12, wherein performing the series of adjustmentscomprises adjusting a policy of the radio access network node.
 14. Themethod of claim 13, wherein the policy comprises at least one of ascheduling policy and a queueing policy.
 15. The method of claim 10,wherein adjusting the buffer parameter comprises switching betweenqueuing schemes or switching between scheduling policies of thecommunication traffic flow.
 16. The method of claim 10, wherein thetarget performance characteristics comprise at least one of a throughputcharacteristic, a latency characteristic or an application burstcharacteristic.
 17. A non-transitory machine-readable medium, comprisingexecutable instructions that, when executed by a processor, facilitateperformance of operations, comprising: monitoring a performance of aflow of communication traffic, wherein the flow of communication trafficuses a group of communication parameters associated with a radio accessnetwork node, wherein the group of communication parameters areadjustable to adjust the flow of the communication traffic; receivingrequested performance characteristics of the performance of the flow ofthe communication traffic; and adjusting a communication parameter ofthe group of communication parameters based on an adjustment value,wherein the adjustment value is determined using the requestedperformance characteristics.
 18. The non-transitory machine-readablemedium of claim 17, wherein the operations further comprise: determiningthat the communication parameter is available for adjustment to satisfythe requested performance characteristics.
 19. The non-transitorymachine-readable medium of claim 18, wherein the operations furthercomprise: performing adjustments to the group of communicationparameters; and analyzing impact of the adjustments on the performanceof the flow of the communication traffic.
 20. The non-transitorymachine-readable medium of claim 17, wherein adjusting the communicationparameter comprises at least one of switching between queuing schemesassociated with the communication traffic or switching betweenscheduling policies associated with the communication traffic.